bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 8 Jan 2021 11:48:25 +0000 (11:48 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Fri, 8 Jan 2021 11:48:25 +0000 (11:48 +0000)
commitde9bafbd3cfb4aeba5b74e22219d3009d9ec3878
tree493361a33136ce6189dd572545ab9db3cf64d2ba
parentaa597400b517468840376ae9ed0ca5f1c1fe87ce
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h